A very dumb problem ocurred:

:kotlinx-coroutines-core:jvmApiCheck in this build failed because atomicfu JVM IR compiler plugin generated some declarations with PUBLIC visibility modifier, and those appeared in the public api, that is obviously not right.

For some reason this simple bug was not revealed by the test build of coroutines with atomicfu JVM IR plugin applied. The config of the build is equal to the train config, actually, but seems that :kotlinx-coroutines-core:jvmApiCheck was not called there at all, I could not find it in the build log.

I filed this issue in kotlinx-atomicfu: Kotlin/kotlinx-atomicfu#258
And prepared a fix for this problem for Kotlin 1.7.21, 1.8.0 and master: https://jetbrains.team/p/kt/reviews/7497/timeline
UPD: the fix is merged

That's too bad, and really reveals the problem of the lack of atomicfu tests and our test train builds ☹️. That code in the atomicfu JVM IR compiler plugin is very old, but we never ran into this issue with visibility modifiers.

I probably need to add some tests to atomicfu-gradle-plugin that would also dump the public api and check that no generated declarations leak

I see that apiCheck is explicitly disabled in these train branches which probably should not be the case

Yes, apiCheck and knitCheck tasks were always excluded in the train builds 😞. I've asked to turn them on.

And I turned on the apiCheck in that test build, now it fails at jvmApiCheck as it should have :(

@mvicsokolova is it safe to merge or we do wait for something else?

Yes I'll merge it. I just forgot to press the button.